NTISthis.com

Evidence Guide: ICTPRG520 - Validate an application design against specifications

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG520 - Validate an application design against specifications

What evidence can you provide to prove your understanding of each of the following citeria?

Evaluate the software requirement specifications

  1. Review the software requirement specifications document prior to design, to ensure that it is complete and correct
  2. Validate the software requirement specifications document
Review the software requirement specifications document prior to design, to ensure that it is complete and correct

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate the software requirement specifications document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create a proof of concept prototype

  1. Use rapid application development tools (RAD) to create a prototype system
  2. Present the prototype system for demonstration to the appropriate person
  3. Validate the proof of concept
Use rapid application development tools (RAD) to create a prototype system

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Present the prototype system for demonstration to the appropriate person

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate the proof of concept

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate the software design

  1. Determine if the design is complete, accurate, consistent and feasible
  2. Validate the software design document
  3. Validate the database structure and its elements
  4. Validate the user interface (UI)
  5. Review the software risk analysis
Determine if the design is complete, accurate, consistent and feasible

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate the software design document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate the database structure and its elements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate the user interface (UI)

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review the software risk analysis

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate the source code

  1. Validate the consistency between the code and the software design document
  2. Validate logical structure and syntax, using static analysis tools
Validate the consistency between the code and the software design document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate logical structure and syntax, using static analysis tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate the testing requirements

  1. Review and validate the test plans
  2. Review and validate the test cases
Review and validate the test plans

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review and validate the test cases

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the validation

  1. Document the results of the validation exercise
  2. Recommend the current software design, or itemise the required alterations
  3. Submit the report to the appropriate person for action
Document the results of the validation exercise

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Recommend the current software design, or itemise the required alterations

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit the report to the appropriate person for action

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Evaluate the software requirement specifications

1.1 Review the software requirement specifications document prior to design, to ensure that it is complete and correct

1.2 Validate the software requirement specifications document

2. Create a proof of concept prototype

2.1 Use rapid application development tools (RAD) to create a prototype system

2.2 Present the prototype system for demonstration to the appropriate person

2.3 Validate the proof of concept

3. Evaluate the software design

3.1 Determine if the design is complete, accurate, consistent and feasible

3.2 Validate the software design document

3.3 Validate the database structure and its elements

3.4 Validate the user interface (UI)

3.5 Review the software risk analysis

4. Evaluate the source code

4.1 Validate the consistency between the code and the software design document

4.2 Validate logical structure and syntax, using static analysis tools

5. Evaluate the testing requirements

5.1 Review and validate the test plans

5.2 Review and validate the test cases

6. Document the validation

6.1 Document the results of the validation exercise

6.2 Recommend the current software design, or itemise the required alterations

6.3 Submit the report to the appropriate person for action

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Evaluate the software requirement specifications

1.1 Review the software requirement specifications document prior to design, to ensure that it is complete and correct

1.2 Validate the software requirement specifications document

2. Create a proof of concept prototype

2.1 Use rapid application development tools (RAD) to create a prototype system

2.2 Present the prototype system for demonstration to the appropriate person

2.3 Validate the proof of concept

3. Evaluate the software design

3.1 Determine if the design is complete, accurate, consistent and feasible

3.2 Validate the software design document

3.3 Validate the database structure and its elements

3.4 Validate the user interface (UI)

3.5 Review the software risk analysis

4. Evaluate the source code

4.1 Validate the consistency between the code and the software design document

4.2 Validate logical structure and syntax, using static analysis tools

5. Evaluate the testing requirements

5.1 Review and validate the test plans

5.2 Review and validate the test cases

6. Document the validation

6.1 Document the results of the validation exercise

6.2 Recommend the current software design, or itemise the required alterations

6.3 Submit the report to the appropriate person for action

Evidence of the ability to:

interpret and check software requirement specifications documents

use rapid application development (RAD) tools to create and present a validated proof of concept prototype

validate the software design, source code and testing requirements and document the results

report on results of validation, including recommended actions.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain the database design and implementation

describe business and technical modelling using UML tools at intermediate level

outline current software development methodologies

describe, in detail, the system development life cycle (SDLC)

explain object-oriented programming

describe open-source development tools

describe software-testing techniques.